Fixes #4153: Handling OpenAI 429's gracefully #4284
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vga91
added a commit
that referenced
this pull request
Dec 11, 2024
vga91
added a commit
to vga91/neo4j-apoc-procedures
that referenced
this pull request
Jan 16, 2025
…o4j-contrib#4284) * Fixes neo4j-contrib#4153: Handling OpenAI 429's gracefully * cleanup * fix tests
vga91
added a commit
that referenced
this pull request
Jan 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4153
Adds a backoff strategy to OpenAI API calls.
To better handle API failures caused by excessive load (HTTP 429 - Too Many Requests), the OpenAI API calls have been wrapped in a method that implements a backoff strategy.
This approach efficiently manages retries, reducing the likelihood of overwhelming the API and enhancing system resilience under high-load conditions.
Changes